-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AG-1471, AG-1473, AG-1474: add workflow to create agora/data Docker image and run end-to-end tests #1311
AG-1471, AG-1473, AG-1474: add workflow to create agora/data Docker image and run end-to-end tests #1311
Conversation
port, | ||
reuseExistingServer: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reuse the existing server rather than having playwright start the server for us
); | ||
let dbUser: string | undefined; | ||
let dbPass: string | undefined; | ||
if (process.env.APP_ENV === 'e2e') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Get credentials from environment variables when running e2e tests
…ve access to secrets
97739dd
to
7e28125
Compare
# Run in Sage repo on develop or main branches | ||
# and on all branches in user-owned forks | ||
if: ${{ github.ref_name == 'develop' || github.ref_name == 'main' || github.actor == github.repository_owner }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forks do not have access to the Sage repo's secrets, so don't run this workflow in the Sage repo on pull_request trigger. Instead, run the workflow when there is a push to develop/main or when the user pushes to a repo that they own (i.e. their forked repo).
Looks great! |
Currently, the workflow builds the agora/data image on the runner and then runs the e2e tests. In a future PR, we'll split this workflow into three jobs:
Note: we will need to add the appropriate environment variables and secrets to this repository before the workflow will run.